Method and device for controlling floor in push to service

ABSTRACT

A PT (e.g., Push-To-Talk, Push-To-View or Push-To-Data) service, and more particularly, to a method and device for controlling a floor (talk burst authority, permission to send media burst, etc.) in a PT service, are discussed. According to an embodiment, the method for controlling a state of a Push-To (PT) server, includes transiting, by a PT server in a second state, to a first state when a media burst release message is received by the PT server; and remaining, by the PT server, in the first state, if the PT server in the first state receives a media packet from a PT client and if the PT server in the previous second state has received the media burst release message.

This application claims the priority benefits of U.S. ProvisionalApplication No. 60/852412 filed on Oct. 18, 2006 and Korean PatentApplication No. 10-2007-0062429 filed on Jun. 25, 2007 in Republic ofKorea, the entire contents of which are herein incorporated byreference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This disclosure relates to a Push-To (PT) (e.g., Push-To-Talk,Push-To-View or Push-To-Data) service, and more particularly, to amethod and device for controlling a floor (talk burst authority or mediaburst authority, permission to send media burst, etc.) in a PT service.

2. Discussion of the Related Art

A PT service is a type of half duplex communication service, such as aPTT (Push to Talk) for providing call services by sending voice (audio)data, a PTV (Push to View) for sending image (video) data, and a PTD(Push to Data) for sending various data. Among clients participated in asession established via a server in the PT service, one client having atalk burst authority (or media burst authority or floor) or a permissionto send media burst sends media data (e.g., talk burst or media burst)including audio or video and then the remaining clients participated inthe session receive the sent media data.

A PT client in the PT service can communicate with a plurality ofdifferent PT clients without having to perform a dialing process, awaiting process for call connection and a call connection tone providingprocess, so that it can support a fast communications service comparedwith an ordinary mobile communications terminal. Also, the PT servicecan send a user's voice and data to a single recipient (1-to-1) or togroups of recipients (1-to-many) as in a group chat session.

The related art PT service comprises selecting, by a specific client,one or more other clients and inviting them in a PT session,establishing a session between the inviting client (originating client)and the invited clients (terminating clients), andtransmitting/receiving voice (audio) and/or other data between theclients having the session established therebetween.

In the PT service, before a user sends media data such as audio, videoor other data via his PT terminal, the user must request a permission tosend media data (or talk burst authority or media burst authority orfloor, which can be referred to as ‘media burst authority’ hereafter)from a PT server (e.g., PoC (Push to Talk over Cellular) server). Theuser can send the media data after being granted the media burstauthority from the PT server. As such, controlling the media burstauthority of the user's terminal is referred to as Talk Burst Control(or Media Burst Control). In addition, regarding this media burstcontrol, the media burst authority with which a specific user can sendmedia data via a communication channel can be restricted, function ofwhich is called ‘Talk Burst Revoke’.

FIG. 1 is a state transition (state machine) diagram of a PT server(from the perspective of the PT server) for a media burst operation to aPT client according to a related art. FIG. 1 illustrates each state ofthe PT server for media burst (or talk burst) operations to the PTclient (i.e., terminal). States illustrated in oval shape in FIG. 1 maybe classified into a stable state and a transition state depending onthe characteristic of each state. Events are indicated in boxes in FIG.1.

Relevant states illustrated in FIG. 1 are described as follows.

(a) ‘Start-stop’ state denotes a state in which no SIP (SessionInitiation Protocol) session exists between a PT server and anassociated PT client. Hereinafter, this ‘Start-stop’ state is referredto as ‘0 (zero) state’.

(b) A state ‘U: not permitted and MB_Idle’ is a stable state, anddenotes a state in which a PT server can receive a talk burst (mediaburst) authority request from a PT client. In other words, it is a statein which the PT client can send a talk burst (media burst) request(referred to as ‘MB_Request) in order to send media burst to the PTserver. Hereinafter, the state ‘U: not permitted and MB_Idle’ isreferred to as a ‘first state’.

(c) A state ‘U: permitted’ is a stable state, and denotes a state inwhich a PT server has granted the permission to send a media burst to anassociated PT client so that the associated PT client can send the mediaburst to the PT server. Hereinafter, this state ‘U: permitted’ isreferred to as a ‘second state’. In this state, the PT server operates(starts) a T1 timer (i.e., End of RTP media timer) and a T2 timer (i.e.,Stop talking timer). These timers will be explained later.

(d) A state ‘U: not permitted but sends media’ is a transition state,and denotes a state in which a PT server receives media date (or RTPmedia packets) from a PT client that does not have a talk burstauthority. Hereinafter, this state ‘U: not permitted but sends media’ isreferred to as a ‘third state’. In this state, the PT serveroperates/starts a T8 timer (i.e., media burst revoke timer).

(e) A state ‘U: pending MB_Revoke’ is a transition state, and a PTserver uses this state during a grace period after sending an MBCP(Media Burst Control Protocol) Media Burst Revoke message. Hereinafter,this state ‘U: pending MB_Revoke’ is referred to as a ‘fourth state’. Inthis state, the PT server operates/starts a T3 timer (i.e., Starttalking grace timer), and a period for which the T3 timer is runningcorresponds to the grace period.

(f) A state ‘U: waiting MB_Revoke’ is a stable state, and denotes astate in which a PT serve does not grant a permission to send a mediaburst requested by an associated PT client for a certain period forwhich a T9 timer is operated/running. When the associated PT clientcontinues sending media data beyond a period of the permission to sendthe media burst (i.e., a period for which the T2 timer is running untilit expires), the PT server panelizes the associated PT client. In thisstate, the PT server operates/starts the T9 timer (i.e., retry-aftertimer). Hereinafter, this state ‘U: waiting MB_Revoke’ is referred to asa ‘fifth state’.

(g) A state ‘U: not permitted and MB₁₃ Taken’ is a stable state, anddenotes a state in which when another PT client (i.e., not associated PTclient), other than the associated PT client which has been permitted tosend a media burst, requests the permission to send a media burst, a PTserver informs the another PT client that the permission to send themedia burst is taken. Hereinafter, this state ‘U: not permitted andMB_Taken’ is referred to as a ‘sixth state’.

The timers T1, T2, T3, T8 and T9 introduced in the above description ofFIG. 1 are used in order to restrain or control the sending of mediaburst (MB) between the PT server and the associated PT client(s).Hereinafter, the operations of these timers are described. Generally,media data sent from a PT client to a PT server is sent in a RTP (RealTime Protocol) packet format.

T1 Timer (End of RTP Media Timer)

T1 timer is adapted to count whether a PT server has received asucceeding RTP packet within an available time period after receiving apreceding RTP packet. The T1 timer is generally set to 4 seconds as itsa default value. After a terminal sends media data, namely, RTP mediapackets, to a PT server, when the PT server receives a first RTP packet,the T1 timer is started, and it is restarted whenever a following RTPpacket is received. When the PT server receives the last RTP packet, theT1 timer is stopped or expires.

T2 Timer (Stop Talking Timer)

T2 timer is adapted to count a permitted (authorized) period for which aterminal having a permission to send a media burst (floor or talk burstauthority) can send media data. When the terminal sends a first RTPpacket, the PT server starts the T2 timer. The T2 timer is generallydefaulted to 30 seconds.

T3 Timer (Stop Talking Grace Timer)

T3 timer is adapted to count a grace period for which the PT server canfurther receive media data even after the T2 timer expires. Here, thegrace period refers to a kind of a marginal excess time for which the PTserver is allowed to receive media data even after the T2 timer expires.That is, even if the terminal having the permission to send the mediaburst has sent the media data after the period for which the terminal ispermitted to send the media data, the PT server permits the media datareceived from the terminal during the set period of the T3 timer, i.e.,before the T3 timer expires.

T9 Timer (Retry-After Timer)

T9 timer is adapted to count a penalty time given to a terminal when itsends the media data beyond a permitted period, the penalty time forwhich the terminal can not be permitted to request the media burstauthority to PT server. When the terminal sends the media data beyond(after) a value (time period) set by the T2 timer (i.e., after apermitted period for sending the media data), the PT server sends a MBCPRevoke message or TBCP Revoke message to the terminal and then startsthe T3 timer. When the PT server may not receive a MBCP Release messageor TBCP Release message from the terminal during the time set by the T3timer, it starts the T9 timer so that the terminal is not permitted torequest the media burst authority and send the media data for a certainperiod corresponding to the time value set by the T9 timer (i.e., duringthe running period of the T9 timer).

T8 Timer (Talk Burst Revoke Timer)

T8 timer is started at the time of sending a MB_Revoke message by the PTserver. When the terminal has not sent a MB_Release message within avalue (i.e., time period) set by the T8 timer, the PT server restartsthe T8 timer to wait to receive the MB_Release message being sent by theterminal.

FIG. 2 is a signal flowchart illustrating acquisition of a permission tosend a media burst and transmission of media data between a PT serverand terminals according to a related art.

Hereinafter, description is provided with reference to FIGS. 1 and 2.Here, it is assumed that a SIP session was initiated in the zero stateof the PT server in FIG. 1, and then the PT sever has been transited(changed) into the first state by sending a MB_Idle message to eachterminal (PT client device). That is, the PT server is in a state inwhich each terminal can request a permission (i.e., media burstauthority) to send a media burst from the PT server.

Each of terminals A, B and C sends to the PT server a message forrequesting a floor (media burst authority or talk burst authority) or apermission to send a media burst (i.e., MB_Request) (S1). If the PTserver has decided to grant a permission to send the media burst to theterminal A, the PT server sends a MB_Granted message to the terminal Ain response of the MB_Request message thereof. In the meantime, the PTserver sends a message indicating the terminal A has taken thepermission to send the media burst (i.e., MB_Taken) to the terminals Band C (S2). Through those steps S1 and S2, an operation state of the PTserver with respect to the terminal A may be transited from the firststate into the second state (i.e., state ‘U: permitted’) as illustratedin FIG. 1. Accordingly, the terminal A can now send media data (or RTPmedia packets) to the PT server within the period set by the T2 timer(i.e., during the running period of the T2 timer). Also, through stepsS1 and S2, since the terminals B and C have received the MB_Takenmessage, the operation state of the PT server with respect to theterminals B and C corresponds to the sixth state (‘U: not permitted andMB_Taken’) as illustrated in FIG. 1.

Because the state of the PT server with respect to the terminal A inFIG. 1 corresponds to the second state (i.e., state ‘U: permitted’), theterminal A can send the media data (or RTP media packets) to the PTserver (S3). Here, when receiving a first RTP media packet sent by theterminal A, the PT server may start both the T1 timer and the T2 timersimultaneously.

If the terminal A sends a message for releasing the permission to sendthe media burst (i.e., MB_Release message) within the period for whichit is permitted to send the media data (i.e., within a value (timeperiod) set by the T2 timer), the state of the PT server with respect tothe terminal A may be transited from the second state into the firststate as illustrated in FIG. 1. Also, the PT server may stop the runningT2 timer (i.e., the T2 timer is stopped before it expires). However, ifthe period for which the terminal A is permitted to send the media data(i.e., the value (time period) set by the T2 timer) expires, the PTserver sends a message for revoking the permission to send the mediaburst (i.e., MS_Revoke message) to the terminal A.

Generally, messages and media data (or RTP media packets) from aterminal may be sent via different network routing paths under aphysical communication environment. However, such physical communicationenvironment may include a transit delay while receiving the messages andthe media data via different network routing paths. In addition, suchsituation may make the current state of the PT server with respect tothe terminal to be the third state (e.g., ‘U: not permitted but sendsmedia’) unintentionally in the state machine diagram of FIG. 1.

For instance, when the PT server is in the second state and thenreceives a MB_Release message from the terminal, the PT server transitsfrom the second state to the first state. If the PT server then receivesmedia data (RTP packet) that was sent out by the terminal earlier thanthe MB_Release message but arrived at the PT server later due to thedelay in the routing path, then the PT server transits from the firststate to the third state as shown in FIG. 1. But the third state is notdesired at this time because the terminal cannot request a permission tosend a media burst from the PT server in the third state, and the PTserver needs to return to the first state in order for the terminal tobe able to request a permission to send a media burst. Further, the PTserver may not be able to return to the first state at that time becauseto do so, the PT server needs to receive another MB_Release messagewhich is unlikely to happen at that time. As a result, the terminalaccording to the state machine diagram of FIG. 1 of the related art maybe kept to remain in the unintended state (e.g., the third state) whereit can not request a permission to send a media burst from the PTserver, which is a problem.

For example, when RTP media packets and MB_Release message aresequentially sent by the terminal, the MB_Release message may be reachedat the PT server earlier than the RTP media packets or vice versa. Inthat case, the PT server can receive a part of the RTP media packets(e.g., the last or another RTP media packet of the RTP media packetssent by the terminal) via certain network routing paths, after receivingthe MB_Release message via other network routing paths. At this time,since the PT server has already received the MB_Release message, thestate of the PT server with respect to the terminal in the state diagramof FIG. 1 is transited from the second state (i.e., ‘U: permitted’) intothe first state (i.e., ‘U: not permitted and MB_Idle’). Afterwards, evenif the PT server has received the last RTP media packet, it can notrecognize that the received last RTP media packet has been sent earlierthan the already received MB_Release message. Accordingly, the PT serverdetermines that the terminal having no permission to send the mediaburst has sent the media data (i.e., the received last RTP mediapacket). Therefore, the PT server discards the received last RTP mediapacket and then sends a MB_Revoke message (indicating that thepermission to send media burst granted to the terminal has been revoked)to the terminal (i.e., this corresponds to ‘Situation 1’ of FIG. 1).That is, in the state diagram of FIG. 1 according to the related art,the state of the PT server with respect to the terminal is changed fromthe first state (i.e., ‘U: not permitted and MB_’) into the third state(i.e., ‘U: not permitted but sends media’). Under the third state ofFIG. 1, the PT server sends the MB_Revoke message to the terminal andsimultaneously operates the T8 timer (i.e., this corresponds to‘Situation 2’ of FIG. 1 ). However, Situation 2 is repeated until the PTserver receives a MB_Release message from the terminal, and the state ofthe PT server with respect to the terminal may keep at the third statein the state machine diagram of FIG. 1. If Situation 2 is repeated, fromthe perspective of the terminal, the terminal may be unfavorably treatedin that it can not request a media burst authority (the permission tosend media burst) to the PT server in spite of having sent theMB_Release message previously. This is a problem which may occur due tothe different network routing paths of the messages sent by theterminal.

In addition, because of the different network routing paths of themessages sent by the terminal, as a result the terminal mayunintentionally reach the fifth state (i.e., U: waiting MB_Revoke) inthe state diagram of FIG. 1. That is, after being granted the permissionto send the media burst, the terminal (or PT client) may send the mediadata (i.e., series of RTP media packets) to the PT server during thepermitted period for sending the media data (i.e., the time periodcorresponding to the set value of the T2 timer). In some cases, theseries of RTP media packets sent by the terminal have sequence numbers.Also, information on the sequence number of the last RTP media packetmay be included in the MB_Release message.

Although the terminal has sequentially sent the series of RTP mediapackets (i.e., media data) and the MB_Release message to the PT serverwithin the set period on the T2 timer (e.g., 30 seconds), the messages(i.e. the RTP media packets and the MB_Release message) may benon-sequentially be received by the PT server, as compared to theirsequential sending, because of their different network routing paths.For example, when RTP media packets and MB_Release message aresequentially sent, MB_Release message may be reached at the PT serverearlier than the RTP media packets. That is, after receiving theMB_Release message sent by the terminal, the PT server may receive apart of the RTP media packets (e.g., the last RTP media packet of theRTP media packets sent by the terminal). Here, the PT server checks(i.e., retrieves and analyzes) the information on the sequence number ofthe last RTP media packet included in the MB_Release message, and thenwaits until the last RTP media packet is received. That is, the state ofthe PT server with respect to the terminal still stays in the secondstate (i.e., State ‘U: permitted’) of FIG. 1. However, if the T2 timerexpires while the PT server waits to receive the last RTP media packet,the PT server sends the MB_Revoke message to the terminal (i.e., thiscorresponds to Situation 3 of FIG. 1). Here, the state of the PT serverwith respect to the terminal is transited from the second state into thefourth state (i.e., State ‘U: pending MB_Revoke’). Afterwards, uponreceiving the last RTP media packet, the PT server may consider the lastreceived RTP media packet as an invalid (not-permitted packet) that hasnot reached within the permitted time period for sending the media data(i.e., the set period of the T2 timer), and thereby penalizes theterminal. Accordingly, the state of the PT server with respect to theterminal is transited from the fourth state into the fifth state (i.e.,State ‘U: waiting MB_Revoke’), namely, into the state in which theterminal is penalized (punished). That is, the terminal in the fifthstate can not request a media burst authority to the PT server for theduration of the penalizing period (i.e., the time period correspondingto the set value of the T9 timer).

Accordingly, in a case where the terminal has sequentially sent RTPmedia packets (media data) and the MB_Release message within thepermitted period for sending the media data (i.e., the time period seton by the T2 timer) (e.g., 30 seconds), if the permitted period forsending the media data elapses under the state that the PT server hasfirst received the MB_Release message but has not received yet a part ofthe RTP media packets (e.g., the last RTP media packet) due to a transitdelay on the network routing paths, the terminal may undesirably be in astate that it can not request media burst authority to the PT server forthe time period set on the T9 timer (e.g., 30 seconds), which is notdesired.

BRIEF SUMMARY OF THE INVENTION

An object of the present invention is to provide a method and device forcontrolling a state of a PT server, which address the limitations anddisadvantageous associated with the related art.

Another object of the present invention is to provide a PT client device(terminal) and a PT server, which can provide effective media burstcontrol techniques.

Further, this disclosure of the present invention is to allow a terminal(PT client device) to request a permission to send media burst (floor ormedia burst authority) even if a PT server receives certain media dataafter receiving a message for releasing the permission to send the mediaburst from the terminal.

This disclosure of the present invention is also to allow a terminal (PTclient device) to request a permission to send a media burst withoutrestricting (restraining or controlling) the request of the terminal forthe permission to send the media burst for a certain time period, evenif a permitted time period for the permission to send the media burstelapses after a PT server receives a message for releasing thepermission to send the media burst from the terminal.

According to an aspect of the present invention, there is provided amethod for controlling a state of a Push-To (PT) server, comprising:transiting, by a PT server in a second state, to a first state when amedia burst release message is received by the PT server; and remaining,by the PT server, in the first state. If the PT server in the firststate receives a media packet from a PT client and if the PT server inthe previous second state has received the media burst release message.

According to another aspect of the present invention, there is provideda method for controlling a state of a Push-To (PT) server, comprising:transiting, by the PT server in the second state, to a first state whenthe media burst release message is received: determining, by the PTserver, if the media burst release message has been received in theprevious second state, when a media packet is received while the PTserver is in the transited first state; and remaining, by the PT server,in the transited first state when the media packet is received, if thedetermining step determines that the media burst release message hasbeen received in the previous second state. The method furthercomprises; receiving, by a PT server in a second state, one or moremedia packets from a PT client while a T2 timer is running; andreceiving, by the PT server in the second state, a media burst releasemessage from the PT client while the T2 timer is running.

According to another aspect of the present invention, there is provideda method for controlling a state of a Push-To (PT) server, comprising:determining, by a PT server in a second state, whether or not a mediaburst release message has been received, on expiry of the timer T2 (whena T2 timer expires); and transiting, by the PT server, either from thesecond state to a first state if the determining step determines thatthe media burst release message has been received, or from the secondstate to a fourth state, based on the determination result.

According to another aspect of the present invention, there is provideda method of controlling state of a Push-To (PT) server, comprising:receiving, by a PT server, a media burst release message while a T2timer is running; determining, by the PT server, whether the media burstrelease message has been received, on expiry of the timer T2 (when theT2 timer expires); and transiting, by the PT server, to a media burstidle state, when the determining step determines that the media burstrelease message has been received.

According to another aspect of the present invention, there is provideda Push-To (PT) client device comprising: a controller to transmit atleast one media packet and a media burst release message to a PT server,to receive a media burst idle message from the PT server in response tothe media burst release message, and to transmit a media burst requestto the PT server after receiving the media burst idle message, whereinthe media burst idle message is received from the PT server if the PTserver has received the media burst release message before a timer T2.

According to another aspect of the present invention, there is provideda Push-To (PT) client device comprising: a controller to transmit atleast one media packet and a media burst release message to a PT server,to receive a media burst idle message from the PT server in response tothe media burst release message, and to transmit a media burst requestto the PT server after receiving the media burst idle message, whereinthe media burst request is transmitted if the PT server receives atleast one media packet in a first state after receiving the media burstrelease message, the media burst release message received in a previousstate by the PT server.

These and other objects of the present application will become morereadily apparent from the detailed description given hereinafter.However, it should be understood that the detailed description andspecific examples, while indicating preferred embodiments of theinvention, are given by way of illustration only, since various changesand modifications within the spirit and scope of the invention willbecome apparent to those skilled in the art from this detaileddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will become more fully understood from thedetailed description given hereinbelow and the accompanying drawingswhich are given by way of illustration only, and thus are not limitativeof the present invention and wherein:

FIG. 1 is a state machine diagram illustrating a transmitting/receivingmedia burst between a PT client and a PT server according to a relatedart;

FIG. 2 is a signal flowchart illustrating acquisition of a permission tosend a media burst and transmission of media data between a PT serverand terminals (PT clients) according to a related art;

FIG. 3 is a signal flowchart illustrating a media burst control inaccordance with a first embodiment of the present invention; and

FIG. 4 is a signal flowchart illustrating a media burst control inaccordance with a second embodiment of the present invention.

FIG. 5 is a PT architecture illustrating a UE (or terminal) of thepresent invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

This disclosure of the preferred embodiments of the present inventionmay be applied to PT communication systems providing PT services andrelated devices. However, this disclosure may not be limited to these,but be applicable to every wired/wireless communication system andrelated device to which technical characteristics of this disclosure canbe applied.

According to one aspect of the present invention, when a terminal havinga permission to send a media burst (floor or media burst authority)sends media data (e.g., RTP media packets having no sequence number) anda message for releasing the permission to send the media burst (i.e.,MB_Release) to a PT server within a period of the permission to send themedia burst, even if the PT server receives a part of the media data(e.g., the last RTP media packet or at least one RTP media packet whichis not the last RTP packet) after receiving the MB_Release message dueto a transit delay on different network routing paths, the terminal canbe allowed to request the permission to send the media burst without anyrestraint by the PT server.

According to another aspect of the present invention, when the terminalhaving the permission to send the media burst sequentially sends mediadata (e.g., RTP media packets having sequence numbers) and theMB_Release message within the period of the permission to send a mediaburst, even if the PT server first receives the MB_Release message dueto the transit delay on different network routing paths, and thenreceives a part of the media data (e.g., the last RTP media packet or atleast one RTP media packet which is not the last RTP packet) untilbefore the period of the permission to send the media burst elapses, theterminal can be allowed to request the permission to send the mediaburst without any restraint.

Hereinafter, constructions and operations of the preferred embodimentsof the present invention will be explained with reference to theaccompanying drawings. This disclosure may propose first and secondembodiments for illustrated examples only.

The first embodiment applies to cases where RTP media packets (mediadata) have sequence numbers or where RTP media packets have no sequencenumbers. The second embodiment preferably applies to a case where RTPmedia packets (media data) have sequence numbers, such that the PTserver knows that one or more additional RTP media packets may bereceived by examining the ‘sequence number of last packet’ informationincluded in a received media burst release message (e.g., MB_Releasemessage) and thus can wait for any additional RTP media packet to bereceived. Here, the sequence number of each RTP media packet (mediadata) acts as an identifier of each packet and also acts as a type of anindicator for informing a sequence (order) of each packet. EachMB_Release message includes information identifying a last RTP mediapacket such as ‘sequence number of last packet’. However, each RTP mediapacket may or may not include its sequence number therein.

FIG. 3 is a signal flowchart illustrating a media burst control inaccordance with the first embodiment of this disclosure.

Hereinafter, description is made with reference to FIGS. 1 and 3. Here,it is assumed that a SIP session is initiated in the zero state of thePT server in FIG. 1, and then the PT sever is in the first state bysending a MB_Idle message to each terminal. That is, each terminal is ina state in which they can request a media burst authority (floor or apermission to send media burst) to the PT server. However, descriptionis given here on the assumption that a terminal A has been granted thepermission to send a media burst from the PT server, only as an example.

Each of terminals A, B and C (PT client devices) sends a message forrequesting a permission to send a media burst (e.g., MB_Request) to thePT server (S10). When the PT server has decided to grant a permission tosend a media burst to the terminal A, it sends to the terminal A agranted message (e.g., MB_Granted) in response of the request for thepermission to send a media burst by the terminal A, but sends to theterminals B and C a message for informing that the permission to send amedia burst has been taken by the terminal A (S20). Through steps S10and S20, a state of the PT server with respect to the terminal A istransited (changed or moved) from the first state of FIG. 1 into thesecond state machine (i.e., State ‘U: permitted’). Therefore, theterminal A can send media data (or RTP media packets) to the PT serverduring a permitted time set on by a T2 timer. Also, through stops S10and S20, the terminals B and C have received a MB-Taken message, andaccordingly, the operation state of the PT server with respect to theterminals B and C corresponds to the six state (State ‘U: not permittedand MB_Taken’) of FIG. 1. Since the terminal A is in the second state(i.e., State ‘U: permitted’), the terminal A can send media data (or RTPmedia packets) to the PT server (S30). Here, when receiving a first RTPmedia packet, the PT server operates both a T1 timer and a T2 timer.That is, the terminal A can send a series of RTP media packets to the PTserver within a time (period) set on by the T2 timer (e.g., 30 seconds)(S31 to S33). Here, the PT server restarts the T1 timer whenever eachRTP media packet is received. The T1 timer counts the period from themoment of receiving one RTP media packet to the moment of receiving thefollowing RTP media packet.

When the T1 timer expires or a MB_Release message is received from theterminal A, the PT server determines that the terminal A has completelysent its media data, and then transits from the second state of FIG. 1into the first state of FIG. 1, namely, into a state in which theterminal A can request a media burst authority (the permission to send amedia burst).

Here, step S30 is explained in more detail. As illustrated in FIG. 3,the terminal A has sent to the PT server a series of RTP media packetswithin a period for which the terminal A is permitted to send the mediadata (i.e., a value (time period) set on by the T2 timer) (S31 to S33),and then has sent a MB_Release message (S34). Here, the messages (i.e.,the RTP media packets and the MB_Release) sent by the terminal A can besent to the PT server via different network routing paths, which canresult in the occurrence of a transit delay due to the use of differentnetwork routing paths. Accordingly, the PT server can receive the lastRTP media packet or one or more RTP media packets (which may not be thelast RTP media packet) after receiving the MB_Release message sent bythe terminal A (S34).

Since the PT server has received the MB_Release message at step S34 whenthe T2 timer is still running, a TBCP (or MBCP) state of the PT serverwith respect to the terminal A is transited from the second state (whichis the current state) (i.e., a State ‘U: permitted’) to the first statemachine (i.e., State ‘U: not permitted and MB_Idle’). The PT server canreceive a message for requesting the permission to send media burst(e.g., MB_Request) from the terminal A, which means the terminal A cansend a media burst request to the PT server again if desired in thisstate.

Then, according to the present invention, as in step S33 if the PTserver staying in the first state receives the last RTP media packet orany other RTP media packet(s), then the PT server determines if aMB_Release message (i.e. the message which the PT server has alreadyreceived in the second state {i.e., State ‘U: permitted}) has beenalready received. If it is determined the MB_Release message has beenalready received, then the PT server does not transit to the third state(‘U: not permitted but sends media’), discards the received last or anyother RTP media packet (without transmitting it to other PT client(s)),and remains in the first state, so the terminal A can request apermission to send a media burst again if desired. On the other hand, ifit is determined the MB_Release message has not been received, then thePT server transits from the first state to the third state.

In the example of FIG. 3, the PT server in the first state determinesthat the MB_Release message (i.e. the message which the PT server hasalready received in the second state {i.e., State ‘U: permitted}) hasbeen received (e.g., at step S34) and thus discards the received RTPmedia packet(s), remains in the first state and does not transit to thethird state (S35), contrary to the related art of FIG. 1. That is, whenthe PT server staying in the first state receives a RTP media packet ofstep S33, the state of the PT server with respect to the terminal A isnot transited from the first state into the third state (i.e., State ‘U:not permitted but sends media’ of FIG. 1). As a result, even though thePT server has received the RTP media packet of step S33 after receivingthe MB_Release message of step S34, the PT server may not decide thatthe terminal A who sent the media data has no permission to send themedia burst.

In the above case, the PT server discards the last RTP media packet (orany other RTP media packet) received at step S33 after the receipt ofthe MB_Release message at step S34, and then allows the terminal A tostill request the permission to send a media burst. That is, the TBCP(or MBCP) state of the PT server with respect to the terminal A is stillstaying at the first state. Therefore, it is possible to prevent theterminal A from being treated unfavorably due to the transit delay onthe network routing paths, when the terminal A has first sent the mediadata (i.e., the series of RTP media packets) within a time (period) seton by the T2 timer, namely, within a period of the permission to send amedia burst and then sent the MB_Release message. Accordingly, the statemachine of the PT server with respect to the terminal is not betransited from the first state into the third state. Hence, according tothe present invention, the terminal A can request a permission to send amedia burst from the PT server again and is not penalized, which isadvantageous and effective.

FIG. 4 is a signal flowchart illustrating a media burst control inaccordance with a second embodiment of this disclosure. Here, it isassumed that a SIP session is initiated in the zero state of the PTserver in FIG. 1, and then the PT sever is in the first slate by sendinga MB_Idle message to each terminal. That is, each terminal is in a stateof being able to requesting a permission to send a media burst from thePT server. However, description is made on the assumption that theterminal A has been granted the permission to send a media burst by thePT server, only as an example. In the second embodiment of FIG. 4,operations and functions of steps (S10 and S20) are the same as stepsS10 and S20 in the first embodiment of FIG. 3. In this example, however,unlike the first embodiment of FIG. 3, in the second embodiment of FIG.4, each of RTP media packets (or media data) has a sequence number, andthe MB_Release message includes information on a sequence number of thelast RTP media packet.

In the second embodiment of the present invention as shown, e.g., inFIG. 4, even if the MB_Release message from the terminal A has beenreceived by the PT server before receiving the last RTP media packet orat least one RTP media packet which may not be the last RTP mediapacket, which was sent earlier than the MB_Release message, the state ofthe PT server is not transited (changed) from the second state into thefirst state, but rather the second state of the PT server still stayswith respect to the terminal A. This indicates that the PT server waitsto receive the last RTP media packet (or any other RTP media packet(s))from the terminal A until the T2 timer expires. In FIG. 4, each RTPmedia packet may have the sequence number so the PT server can wait forthe last packet in view of the ‘sequence number of last packet’information contained in the received MB_Release message.

Also, the second embodiment of FIG. 4 illustrates that, although theseries of RTP media packets (preferably having sequence numbers) and theMB_Release message were sent to the PT server by the terminal A beforethe T2 timer expired, the MB_Release message may first be received bythe PT server due to a transit delay on network routing paths. As aresult, the T2 timer would expire in a state that the PT server has notreceived a part of the RTP media packets (e.g., the last or at least oneRTP media packet). The operations associated with the receipt of theMB_Release message and any RTP media packet by the PT server will now beexplained in more detail referring to step S40 according to the presentinvention.

Referring to step S40, the terminal A having the permission to send amedia burst sends to the PT server a series of RTP media packets withina period for which the terminal A is permitted to send the media data(i.e., a value (time period) set on by the T2 timer) (S41 to S43). Here,preferably each of the RTP media packets has a sequence number. Theterminal A then sends a MB_Release message to the PT server during theperiod for sending the media data (i.e., the value (time period) set bythe T2 timer) (S44). However, even if the RTP media packets and theMB_Release message have sequentially been sent to the PT server by theterminal A, each RTP media packet and the MB_Release message may be sentvia different network routing path. Accordingly, a transit delay mayoccur due to the different routing paths through which the packets andthe message have been sent.

In the example of FIG. 4, before the T2 timer expires, the PT serverreceives a RTP media packet (sequence number 1), a RTP media packet(sequence number 2), and so on (S41 and S42). Afterwards, the PT servermay first receive a MB_Release message before receiving the last or anyother RTP media packet (e.g., a RTP media packet with a sequence numbern) due to the transit delay (S43 and S44). Here, the PT server candetermine if the received RTP media packet is the last RTP media packetby analyzing information on the sequence number (e.g., n) of the lastRTP media packet included in the received MB_Release message. Forinstance, the ‘sequence number of last packet’ information/parameterprovided in the received MB_Release message may be examined. The PTserver can then store the information on the sequence number of the lastRTP media packet in a specific memory (e.g., a memory built in (equippedwith) the PT server or an external memory).

Since the ‘sequence number of last packet’ information included in thereceived MB_Release indicates that the PT server still needs to receivethe last packet, the PT server waits to receive the last RTP mediapacket (with the sequence number n) of step S43 when the PT serverreceives the MB_Release message. And, the state of the PT server withrespect to the terminal A is not transited from the second state to thefirst state, but rather the PT server remains in the second state atthis time (S45) according to the present invention. As a result the PTserver can receive media data (e.g., the last RTP media packet with thesequence number n) sent by the terminal A before the T2 timer expires.

If, however, the last RTP media packet (with the sequence number n) isnot received when the T2 timer expires (e.g., in step S43, the last RTPmedia packet is received after the T2 timer expires), then the PT serverdetermines whether or not it has already received the MB_Release message(S46). That is, when the T2 timer expires while the PT server is in thesecond state (‘U: permitted’), the PT server does not transit to thefourth state, but remains in the second state (S45), and then determinesif the MB_Release message has been already received by the PT server(S46). If it is determined that the MB_Release message has been alreadyreceived, then the PT server transits from the second state to the firststate (‘U: not permitted and MB_Idle’), transmits a MB_Idle message tothe terminal A, and discards any RTP media packet received thereafter.In the example of FIG. 4, since the PT server already has received theMB_Release message at step S44, the PT server at step S45 determinesthat the MB_Release message has been already received, then transitsfrom the second state to the first state, and then transmits a MB_Idlemessage to the terminal A while remaining in the first state (S47 andS48).

On the other hand, if the PT server at step S45 determines that theMB_Release has not been received, then the PT server sends a MB_Revokemessage to the terminal A (S49) and transits from the second state tothe fourth state (‘U: pending MB_Revoke’) (S50).

As discussed above, according to the determination at step S45, the PTserver can know it has already received the MB_Release message at stepS44 before the T2 timer expires. Therefore, the PT server is transitedfrom the second state into the first state such that the terminal A canrequest a permission to send a media burst, which is advantageous. Thatis, the PT server does not send the MB_Revoke message to the terminal Aas soon as the T2 timer expires according to the present invention. Inaddition, the state of the PT server with respect to the terminal A isnot transited (changed) from the second state into the fourth state(i.e., State ‘U: pending MB Revoke’) in this case. However, if it isdetermined at step S45 that the PT server has not yet received theMB_Release message at the time point when the T2 timer expires, the PTserver sends the MB_Revoke message to the terminal A (S49). Here, thestate of the PT server with respect to the terminal A is transited fromthe second state into the fourth state (i.e., State ‘U: pendingMB_Revoke’)(S50).

In the meantime, the PT server can operate the T3 timer when the T2timer expires. If the PT server receives the last RTP media packet (withthe sequence number n) before the T3 timer expires, the PT server sendsthe last RTP media packet (with the sequence number n) to the terminal Band/or the terminal C (i.e., corresponding to Situation 4 of FIG. 1),However, when the T3 timer expires or the PT server staying in thefourth state receives the last RTP media packet (with the sequencenumber n), the PT server shall consider that the terminal A has sent themedia data (i.e., the last RTP media packet with the sequence number n)without the media burst authority (the permission to send a mediaburst). Accordingly, the state of the PT server with respect to theterminal A shall be transited (changed) from the fourth state (i.e.,state ‘U; pending MB_Revoke’) into the fifth-state (i.e., state ‘U:waiting MB_Revoke’). Under the fifth state, the PT server penalizes theterminal A hot to request the permission to send a media burst for acertain period (i.e., for a period set on by the T9 timer).

Therefore, in the second embodiment of the present invention, if the PTserver has received the MB_Release message before receiving the last RTPmedia packet from the terminal A within the permitted period of the T2timer, the PT server checks (analyzes) the information related to thesequence number of the last RTP media packet included in the MB_Releasemessage, and then waits to receive the last RTP media packet by nottransiting from the second state to the first state. However, even ifthe PT server has not received the last RTP media packet at the timewhen the T2 timer expires, the PT server does not automatically send theMB_Revoke message to the terminal A but determines if the MB_Releasemessage has been received and may move from the second state to thefourth state based on this determination. In the related art, the PTserver transits automatically from the second state to the fourth statewhen the T2 timer expires, which causes the timers T3 and T9 to run,during which time of T9 the terminal cannot request a permission to senda media burst. This is a problem because it penalizes the terminal tooseverely. The present invention address this limitation because the PTserver selectively transits from the second state to the fourth statebased on the result of the determination step S46. As a result,according to the present invention, the user (Terminal A) is notpenalized unnecessary and the PT server can allow the terminal A torequest a permission to send a media burst. Therefore, the terminal Acan desirably be provided with the PT service without any restrictiondue to the network transit delay.

As described above, this disclosure of the present invention has beenexplained with reference to the embodiments which are merely exemplary.It will be apparent to those skilled in the art that variousmodifications and variations can be made in this disclosure. Forexample, the methods of the present invention discussed herein can beimplemented by software, hardware, or a combination thereof, namely, itcan be stored in a storage medium (e.g., an inner memory of a terminal,a flash memory, hard disc, etc.), and also be implemented as codes orcommand words within a software program which can be performed by aprocessor (e.g., an inner microprocessor of the terminal). Also, in theembodiments of the present invention, a talk burst indicates audio dataand a media burst indicates data such as characters, moving images, orphotos. The talk burst and the media burst can all be applied to theembodiments of this disclosure regardless of data formats. Thus, it isintended that this disclosure cover modifications and variations of thisinvention provided they come within the scope of the appended claims andtheir equivalents.

Each terminal (e.g., terminal A, B, C, etc.) according to the presentinvention is a PT client device (any device having a PT client) capableof providing a PT service. Each terminal can include a controller, amemory, and any other component(s) for implementing the methods of thepresent invention discussed herein. For instance, each terminal may beone of all types of mobile communications terminals, PT serviceavailable notebooks, desktop computers, portable game devices, MPS, orother home appliances. Also, in the description of the presentinvention, each terminal preferably denotes a physical entity includinga PT client, and the PT client preferably denotes a logical or physicalentity included in the terminal. Accordingly, for the sake of theexplanation of the present invention, the terminal may be referred to asa PT client device or vice-versa.

FIG. 5 is a PT (Push To) system architecture including configuration ofa terminal (or UE) in accordance with the present invention.Hereinafter, description will be made with reference to the FIG. 5.

In the example of FIG. 5, the PT client may reside on the mobileterminal and is used to access the PT service. The PT client may beconfigured to allow PT session initiation, (e.g., codec negotiation),participation (e.g., talk or listen) and release. The PT client may beconfigured to perform registration with a SIP/IP Core and authenticate aPT user to a SIP/IP Core. The PT client may be configured to generateand send Talk Bursts (Media Bursts) by recording and encoding audio. ThePT client may be configured to receive Talk Bursts and generate audio bydecoding the received Talk Bursts. The PT client may be configured tosupport Talk Burst Control procedures and Talk Burst Control Protocolnegotiation. The PT client may be configured to incorporate PTconfiguration data provided by the DM client. The PT client may beconfigured to support the capability to set the Answer Mode Indication(Manual Answer, Automatic Answer), the incoming PT Session Barring andIncoming Instant Personal Alert Barring and Simultaneous PT SessionsSupport. The PT client may be configured to Support User Planeadaptation procedures if initiated by the PT server. The PT client maybe configured to support receiving of Instant Personal Alert. The PTclient may be configured to support sending of Instant Personal Alertand provide Group Advertisement. The PT client may be configured tosupport multiple Talk Burst Control Protocols and Talk Burst requestqueuing that may be based on priority or timestamp. The PT client may beconfigured to send quality feedback reports after end of Talk Burst. ThePT client may be configured to support for Pre-established Sessions. ThePT client may be configured to support Simultaneous Sessions and Sessionon-hold procedures, to request privacy for User identity.

In the example of FIG. 5, XDMC (XML Document Management Client) may bean XCAP client which manages XML documents stored in the network (e.g.,PT-specific documents in the PT XDMS, URI lists used as for example,Contact Lists in the Shared XDMS, etc.). Management features includeoperations such as create, modify, retrieve and delete.

In the example of FIG. 5, the Presence Source is an entity that provides(publishes) presence information to a Presence service. The Watcher isan entity that requests presence information about a Presently, orWatcher Information about a Watcher, form the Presence service.

As discussed above, in this disclosure, the terminal can request apermission to send a media burst (talk burst authority or media burstauthority or floor) without any restraint of the PT server due to thenetwork transit delay. Therefore, the terminal and the PT server can usethe PT service smoothly and desirably.

The present invention has been explained with reference to theembodiments which are merely exemplary. It will be apparent to thoseskilled in the art that various modifications and variations can be madein the present invention without departing from the spirit or scope ofthe invention. Thus, it is intended that the present invention covermodifications and variations of this invention provided they come withinthe scope of the appended claims and their equivalents.

1. A method for controlling a state of a Push-To (PT) server,comprising: transiting, by a PT server in a second state, to a firststate when a media burst release message is received by the PT server;and remaining, by the PT server, in the first state, if the PT server inthe first state receives at least one media packet from a PT client andif the PT server in the previous second state has received the mediaburst release message.
 2. The method of claim 1, wherein the first stateis a state in which the PT client can send a media burst request to thePT server, and the second state is a state in which the PT server hasgranted a permission to send a media burst to the PT client.
 3. Themethod of claim 1, wherein the first state is a “U: not permitted andMB_Idle” state, and the second state is a “U: permitted” state.
 4. Themethod of claim 1, wherein in the transiting step, the PT server in thesecond state receives the media burst release message while a T2 timeris running.
 5. A method for controlling a state of a Push-To (PT)server, comprising: transiting, by the PT server in the second state, toa first state when the media burst release message is received;determining, by the PT server, whether the media burst release messagehas been received in the previous second state when a media packet isreceived while the PT server is in the transited first state; andremaining, by the PT server, in the transited first state when the mediapacket is received, if the determining step determines that the mediaburst release message has been received in the previous second state. 6.The method of claim 5, further comprising: receiving, by a PT server ina second state, one or more media packets from a PT client while a T2timer is running; and receiving, by the PT server in the second state, amedia burst release message from the PT client while the T2 timer isrunning.
 7. The method of claim 5, wherein the first state is a state inwhich the PT client can send a media burst request to the PT server, andthe second state is a state in which the PT server has granted apermission to send a media burst to the PT client.
 8. The method ofclaim 5, wherein the first state is a “U: not permitted and MB_Idle”state, and the second state is a “U: permitted” state.
 9. A method forcontrolling a state of a Push-To (PT) server, comprising: determining,by a PT server in a second state, whether or not a media burst releasemessage has been received, on expiry of a T2 timer; and transiting, bythe PT server, either from the second state to a first state if thedetermining step determines that the media burst release message hasbeen received, or from the second state to a fourth state based on thedetermination result.
 10. The method of claim 9, wherein the first stateis a state in which the PT client can send a media burst request to thePT server, and the second state is a state in which the PT server hasgranted a permission to send a media burst to the PT client.
 11. Themethod of claim 9, wherein the first state is a “U: not permitted andMB_Idle” state, and the second state is a “U: permitted” state.
 12. Themethod of claim 9, wherein in the transiting step, the PT servertransits from the second state to the fourth state on expiry of thetimer T2, if the determining step determines that the media burstrelease message has not been received.
 13. The method of claim 12,wherein the second state is a state in which the PT server has granted apermission to send a media burst to the PT client, and the fourth stateis a state having a grace period during which the PT client is preventedfrom requesting a media burst to the PT server or during which the PTserver can transmit an additional media packet received from the PTclient to another PT client.
 14. The method of claim 12, wherein thesecond state is a “U: permitted” state, and the fourth state is a“U:pending MB_Revoke” state.
 15. A method of controlling state of aPush-To (PT) server, comprising; receiving, by a PT server, a mediaburst release message while a T2 timer is running; determining, by thePT server, whether the media burst release message has been received, anexpiry of the timer T2; and transiting, by the PT server, to a mediaburst idle state, when the determining step determines that the mediaburst release message has been received.
 16. The method of claim 15,wherein the media burst idle state is a “U: not permitted and MB_Idle”state.
 17. A Push-To (PT) client device comprising: a controller totransmit at least one media packet and a media burst release message toa PT server, to receive a media burst idle message from the PT server inresponse to the media burst release message, and to transmit a mediaburst request to the PT server after receiving the media burst idlemessage, wherein the media burst idle message is received from the PTserver if the PT server has received the media burst release messagebefore a T2 timer expires.
 18. The PT client device of claim 17, whereinthe controller is excluded from receiving a media burst revoke messagefrom the PT server due to the receipt of the media burst release messageby the PT server before the T2 timer expires.
 19. A Push-To (PT) clientdevice comprising; a controller to transmit at least one media packetand a media burst release message to a PT server, to receive a mediaburst idle message from the PT server in response to the media burstrelease message, and to transmit a media burst request to the PT serverafter receiving the media burst idle message, wherein the media burstrequest is transmitted if the PT server receives at least one mediapacket in a first state after receiving the media burst release message,the media burnt release message received in a previous state by the PTserver.
 20. The PT client device of claim 19, wherein the PT client istransited from a second state into the first state by the PT serverafter receiving the media burst release message.
 21. The PT clientdevice of claim 19, wherein the previous state is ‘U:permitted’ state.22. The method of claim 20, wherein the first state is a state in whichthe PT client can send a media burst request to the PT server, and thesecond state is a state in which the PT server has granted a permissionto send a media burst to the PT client.